Triple
T37142287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevrast |
E920146
|
entity |
| Predicate | precedesFoundingOf |
P1478
|
FINISHED |
| Object | Gondolin |
—
|
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: Gondolin | Statement: [Nevrast, precedesFoundingOf, Gondolin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesFoundingOf Context triple: [Nevrast, precedesFoundingOf, Gondolin]
-
A.
foundedBefore
chosen
Indicates that one entity was established or created at an earlier time than the other entity.
-
B.
foundedInOrBefore
Indicates that the founding of one entity occurred in a specified year or any earlier year.
-
C.
foundingOf
Indicates the event or relationship in which an entity is established or created, typically linking the founder(s), the founded entity, and the time or context of its creation.
-
D.
foundedAfterArrivalOf
Indicates that one entity was founded only after the arrival or appearance of another specified entity.
-
E.
foundingAround
Indicates that an entity was founded at approximately, but not exactly, the specified time or within a loosely defined surrounding period.
- 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: May 3, 2026, 4:15 p.m.