Triple
T25475094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grail |
E638409
|
entity |
| Predicate | developedByCountryOfSystem |
P79843
|
FINISHED |
| Object | Soviet Union |
—
|
NE NERFINISHED |
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: [Grail, developedByCountryOfSystem, Soviet Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedByCountryOfSystem Context triple: [Grail, developedByCountryOfSystem, Soviet Union]
-
A.
countryOfDeveloper
chosen
Indicates the country in which the developer of an entity (such as a product, software, or work) is based or originates.
-
B.
developedSystemFor
Indicates that one entity created or engineered a system intended to be used by or on behalf of another entity.
-
C.
wasDevelopedIn
Indicates that an entity (such as a product, technology, or work) came into existence or was created during a specific time period or at a particular place.
-
D.
alsoDevelopedIn
Indicates that something was additionally developed in another context, location, or environment beyond the primary one already specified.
-
E.
developedAs
Indicates that one entity was created, designed, or evolved specifically to function as or replace another entity.
- F. None of above.
Provenance (3 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f754447c8190acc16c440f8bb03d |
completed | May 2, 2026, 1:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 2:25 p.m.