Triple
T36546873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hildórien |
E901161
|
entity |
| Predicate | governedByAtAwakening |
P5449
|
FINISHED |
| Object | none (Men were free) |
—
|
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: none (Men were free) | Statement: [Hildórien, governedByAtAwakening, none (Men were free)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedByAtAwakening Context triple: [Hildórien, governedByAtAwakening, none (Men were free)]
-
A.
governedFrom
Indicates that an entity exercises governing authority or administrative control over another entity from a specific location or seat of power.
-
B.
governedByAtTimeOfEvent
chosen
Indicates that an entity is under the authority or control of a particular governing agent specifically at the time a given event occurs.
-
C.
governedIn
Indicates that one entity exercised governing authority or administrative control within a specified place or jurisdiction.
-
D.
areGovernedBy
Indicates that one or more entities are under the authority, control, or administration of a governing body or ruler.
-
E.
laterGovernedAs
Indicates that an entity subsequently held governing authority over another entity at a later time.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a02f2d6f35481909829d4ec710dcb0f |
completed | May 12, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_6a02f15a2460819080cb4be5b50221d0 |
completed | May 12, 2026, 9:22 a.m. |
Created at: May 3, 2026, 4:11 p.m.