Triple
T30633058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tol-in-Gaurhoth |
E779760
|
entity |
| Predicate | statusAfterEvents |
P195315
|
FINISHED |
| Object | ruined |
—
|
LITERAL 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: ruined | Statement: [Tol-in-Gaurhoth, statusAfterEvents, ruined]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterEvents Context triple: [Tol-in-Gaurhoth, statusAfterEvents, ruined]
-
A.
statusAfterMission
Indicates the condition or state an entity is in following the completion of a mission.
-
B.
statusAfterBattle
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
-
C.
legalStatusAfterEvent
Indicates the legal condition or classification an entity has as a result of a specified event or occurrence.
-
D.
statusAfter1598
Indicates the status or condition of an entity as it exists after the year 1598.
-
E.
statusAfter1808
Indicates the condition or classification of something as it existed or was defined after the year 1808.
- F. None of above. chosen
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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
| PDg | Predicate description generation | batch_69fdbaa1313081908beea28a5597ae40 |
completed | May 8, 2026, 10:27 a.m. |
Created at: April 29, 2026, 8:28 p.m.