Triple
T5013209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Jones |
E112675
|
entity |
| Predicate | hasAliasType |
P46146
|
FINISHED |
| Object | false identity |
—
|
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: false identity | Statement: [John Jones, hasAliasType, false identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAliasType Context triple: [John Jones, hasAliasType, false identity]
-
A.
hasAliasReference
chosen
Indicates that one entity serves as an alternate name or alias referring to another entity.
-
B.
hasAlternateMemberType
Indicates that an entity is associated with a different or substitute type of member than its primary or standard member type.
-
C.
hasTypeName
Indicates that an entity is associated with a specific type name used to classify or identify its kind.
-
D.
hasAlignmentType
Indicates that an entity possesses a specific alignment category or classification, such as moral, structural, or directional alignment.
-
E.
hasActingType
Indicates that an entity participates in or performs an action in a specified manner, role, or mode of acting.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd730f12a481908a27c15dc73987c6 |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.