Triple
T11859052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J’adore |
E282112
|
entity |
| Predicate | flanker |
P20134
|
FINISHED |
| Object | J’adore L’Or |
—
|
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: J’adore L’Or | Statement: [J’adore, flanker, J’adore L’Or]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flanker Context triple: [J’adore, flanker, J’adore L’Or]
-
A.
hasFlanker
Indicates that an entity is positioned or assigned as a flanking support or protection alongside another entity.
-
B.
allianceFlank
Indicates a cooperative maneuver where allied entities position themselves on the side of a common target or objective to gain a tactical advantage.
-
C.
liesOnFlankOf
chosen
Indicates that one entity is positioned along the side or lateral edge of another entity.
-
D.
defender
Indicates a relationship where one entity protects, guards, or supports another entity against threats, attacks, or criticism.
-
E.
frontLine
Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a69a099c8190a674db64c50eca5a |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.