Triple
T28273257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragon Warrior |
E712911
|
entity |
| Predicate | speciesOfBearer |
P170660
|
FINISHED |
| Object | giant panda |
—
|
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: giant panda | Statement: [Dragon Warrior, speciesOfBearer, giant panda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speciesOfBearer Context triple: [Dragon Warrior, speciesOfBearer, giant panda]
-
A.
bearerAnglicizedNameOf
Indicates that one entity is the anglicized (English-adapted) version of the name borne by another entity.
-
B.
nameBearerType
Indicates the specific role or capacity in which an entity bears or carries a given name (e.g., as a person, place, organization, or other type of name bearer).
-
C.
occupationOfBearer
Indicates that a specified occupation or job role is held by the bearer entity.
-
D.
notableBearerVariantOf
Indicates that one entity is a notable or prominent variant or version of another entity that bears or carries its characteristics.
-
E.
issuerType
Indicates the classification or category of the entity that issues something (such as a document, credential, or instrument).
- 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 27, 2026, 11:19 p.m.