Triple
T29910563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NameDrop |
E759667
|
entity |
| Predicate | dataTypeShared |
P168245
|
FINISHED |
| Object | phone numbers |
—
|
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: phone numbers | Statement: [NameDrop, dataTypeShared, phone numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataTypeShared Context triple: [NameDrop, dataTypeShared, phone numbers]
-
A.
dataTypeContributed
Indicates that an entity has provided or supplied a particular type or category of data.
-
B.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
-
C.
dataTypeModel
Indicates that one entity serves as the data type or schema model that defines the structure or format of another entity.
-
D.
dataTypes
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
-
E.
dataDatatype
Indicates that a piece of data is associated with, or constrained to, a specific datatype.
- F. None of above. chosen
Provenance (4 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67759bd888190b1beb2fad6058b4d |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:10 p.m.