Triple
T23312994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darwin Information Typing Architecture |
E590630
|
entity |
| Predicate | definesTopicType |
P56536
|
FINISHED |
| Object | concept topic |
—
|
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: concept topic | Statement: [Darwin Information Typing Architecture, definesTopicType, concept topic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesTopicType Context triple: [Darwin Information Typing Architecture, definesTopicType, concept topic]
-
A.
definitionType
Indicates the specific kind or category of definition that characterizes how one entity is defined in relation to another.
-
B.
definesType
chosen
Indicates that one entity specifies or establishes the type or classification of another entity.
-
C.
hasTopicType
Indicates that something is associated with, or categorized under, a particular type of topic.
-
D.
definesMessageType
Indicates that one entity specifies or determines the message type classification or category for another entity.
-
E.
documentationTopic
Indicates that one entity serves as the subject or focus of documentation related 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972ca70481909e2415c65964210a |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:06 p.m.