Triple
T7097496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lions |
E165368
|
entity |
| Predicate | associatedWithCrestElement |
P48367
|
FINISHED |
| Object | lion |
—
|
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: lion | Statement: [The Lions, associatedWithCrestElement, lion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCrestElement Context triple: [The Lions, associatedWithCrestElement, lion]
-
A.
associatedWithElement
chosen
Indicates a relationship where one entity is linked or connected to a particular element, such that the element is relevant to, involved in, or characteristic of that entity.
-
B.
associatedWithFront
Indicates a relationship where one entity is linked or connected specifically to the front part, side, or face of another entity.
-
C.
associatedWithMatch
Indicates a relationship where an entity is linked or connected to a particular match or matching event.
-
D.
associatedWithArena
Indicates a relationship in which an entity is linked or connected to a particular arena, such as by location, use, affiliation, or operation.
-
E.
associatedWithTeamIdentity
Indicates that an entity has a connection or relevance to the identity, branding, or defining characteristics of a particular team.
- 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_69c6887e8c10819091cee237560d32da |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5561dd08190be6b784754a0c1bc |
completed | March 27, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:41 p.m.