Triple
T23156936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Long |
E578464
|
entity |
| Predicate | canReferToMultiplePeople |
P29734
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mike Long, canReferToMultiplePeople, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canReferToMultiplePeople Context triple: [Mike Long, canReferToMultiplePeople, true]
-
A.
canReferToMultipleIndividuals
chosen
Indicates that a single reference, term, or identifier may correspond to more than one individual rather than uniquely identifying just one.
-
B.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to another entity.
-
C.
refersToPerson
Indicates that one entity is making reference to, mentioning, or pointing specifically to a particular person.
-
D.
appliesToPerson
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific person.
-
E.
canLiaiseWith
Indicates that one entity is able or permitted to communicate and coordinate directly with another entity for collaboration or information exchange.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18efe1b0081908e81b757d64c067c |
completed | April 29, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.