Triple
T32050331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thos. Greene |
E818473
|
entity |
| Predicate | notUniqueIdentifierOfSinglePerson |
P86838
|
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: [Thos. Greene, notUniqueIdentifierOfSinglePerson, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notUniqueIdentifierOfSinglePerson Context triple: [Thos. Greene, notUniqueIdentifierOfSinglePerson, true]
-
A.
hasMultipleIdentities
Indicates that a single entity is associated with more than one distinct identity or persona.
-
B.
alternativeIdentification
chosen
Indicates that one entity serves as an alternative identifier or reference for another entity.
-
C.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
D.
hasNoPersonalNameIn
Indicates that an entity lacks a specific personal name within a given context, language, or naming system.
-
E.
identifiedUsing
Indicates that one entity was recognized, distinguished, or determined by means of a specified method, tool, or identifier.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4c884148190be2cb7d9b354d17f |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:20 a.m.