Triple
T26394926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Greenglass |
E663520
|
entity |
| Predicate | covertAllegiance |
P53264
|
FINISHED |
| Object | Soviet Union |
E363
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Soviet Union | Statement: [David Greenglass, covertAllegiance, Soviet Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: covertAllegiance Context triple: [David Greenglass, covertAllegiance, Soviet Union]
-
A.
changeOfAllegiance
Indicates a shift in loyalty or support from one party, group, or cause to another.
-
B.
hadAllegiance
chosen
Indicates that an entity was loyally committed or formally bound in support or service to another entity, such as a person, group, or cause.
-
C.
refusedAllegianceTo
Indicates that one entity declined or rejected giving loyalty, support, or obedience to another entity.
-
D.
allegiance
Indicates a relationship where one entity is loyal, committed, or obligated in support or service to another entity.
-
E.
namedForAllegiance
Indicates that an entity is named in reference to, or in honor of, a particular allegiance, affiliation, or loyalty.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a119a3a0cc88190b94f2ad8ec3b2851 |
completed | May 23, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 26, 2026, 11:28 p.m.