Triple
T26387295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Leach |
E663315
|
entity |
| Predicate | thematicInterest |
P28568
|
FINISHED |
| Object | pirates |
—
|
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: pirates | Statement: [Mike Leach, thematicInterest, pirates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thematicInterest Context triple: [Mike Leach, thematicInterest, pirates]
-
A.
subjectInterest
Indicates that the subject has an interest in, or is concerned with, the object.
-
B.
thematicConcept
Indicates that one entity embodies, expresses, or is centrally concerned with a particular underlying theme or conceptual idea represented by the other entity.
-
C.
thematicArea
chosen
Indicates the subject or item is associated with, or falls under, a particular thematic area or topic of focus.
-
D.
culturalInterest
Indicates a relationship where one entity has an interest in, appreciation for, or engagement with the culture, traditions, or cultural expressions associated with another entity.
-
E.
primaryInterest
Indicates that one entity is the main or most significant focus of attention, concern, or engagement for 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 26, 2026, 11:23 p.m.