Triple
T36547470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Finarfin |
E901173
|
entity |
| Predicate | reputationAmongElves |
P61188
|
FINISHED |
| Object | wise |
—
|
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: wise | Statement: [House of Finarfin, reputationAmongElves, wise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reputationAmongElves Context triple: [House of Finarfin, reputationAmongElves, wise]
-
A.
reputationInLore
Indicates how an entity is regarded or reputed within a fictional or narrative lore context.
-
B.
mythicReputation
Indicates a reputation or renown of legendary, larger-than-life status associated with an entity.
-
C.
hasReputationAmong
chosen
Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
-
D.
refersToPersonReputation
Indicates that something is about, concerns, or makes reference to a particular person's reputation.
-
E.
enthusiastReputation
Indicates that an entity is recognized or regarded as an enthusiast, reflecting a reputation for strong interest or passion in a particular domain or activity.
- 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_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.