Triple
T7099613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eagles of América |
E165421
|
entity |
| Predicate | denotesReputation |
P11701
|
FINISHED |
| Object | strength |
—
|
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: strength | Statement: [Eagles of América, denotesReputation, strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesReputation Context triple: [Eagles of América, denotesReputation, strength]
-
A.
associatedWithReputation
chosen
Indicates a relationship where an entity is linked to, influenced by, or characterized in terms of another entity’s reputation or perceived standing.
-
B.
hasReputationAmong
Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
-
C.
scoringReputation
Indicates that one entity evaluates and assigns a reputation-related score to another entity based on its behavior or performance.
-
D.
laterReputation
Indicates that an entity’s reputation or status at a later time is being referred to in relation to an earlier point or context.
-
E.
reputationBuiltFor
Indicates that one entity has established or developed a reputation specifically for or in relation to 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_69c6887fcddc8190a5d58908f6dee590 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e58531c88190a32746f9a97da709 |
completed | March 27, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:42 p.m.