Triple
T35858424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chida |
E1036571
|
entity |
| Predicate | hasNameProperty |
P75425
|
FINISHED |
| Object | can identify an individual person |
—
|
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: can identify an individual person | Statement: [Chida, hasNameProperty, can identify an individual person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameProperty Context triple: [Chida, hasNameProperty, can identify an individual person]
-
A.
hasProperName
Indicates that an entity is associated with a specific proper name used to uniquely identify it.
-
B.
hasNameFunction
Indicates that an entity is associated with a function whose purpose is to provide or determine its name.
-
C.
hasNotablePropertyNamedAfter
Indicates that an entity possesses a notable property or attribute that is named in honor of, or derived from, another entity.
-
D.
hasNameCharacteristic
chosen
Indicates that an entity possesses a specific quality or attribute related to its name.
-
E.
hasProperNameElement
Indicates that an entity’s proper name includes a specific component (such as a word, phrase, or segment) as one of its constituent elements.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff63e6b61081909c648bf0ff279481 |
completed | May 9, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ff6381867881908ae0545df4b71df5 |
completed | May 9, 2026, 4:40 p.m. |
Created at: May 3, 2026, 4:06 p.m.