Triple
T32454701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Who’s Who |
E829390
|
entity |
| Predicate | entryFeatures |
P80690
|
FINISHED |
| Object | personal details |
—
|
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: personal details | Statement: [Who’s Who, entryFeatures, personal details]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryFeatures Context triple: [Who’s Who, entryFeatures, personal details]
-
A.
entryDescription
Indicates that a text provides a descriptive summary or explanation of a particular entry or record.
-
B.
doorwayFeature
Indicates that one entity is a feature, characteristic, or structural element specifically associated with a doorway of another entity.
-
C.
featuresIn
chosen
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
D.
entryMode
Indicates the manner or method by which something is entered, recorded, or input into a system or context.
-
E.
entryFor
Indicates that one entity serves as the specific record, representation, or listing corresponding to 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_69f3491df9288190afc0b23b1d6e72ce |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c3155c448190b71704970c2cf0e6 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6ba700a708190ab6db62791e43774 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:56 a.m.