Triple
T35945014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cephalotus |
E1039563
|
entity |
| Predicate | leafSpecialization |
P572
|
FINISHED |
| Object | pitcher leaves |
—
|
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: pitcher leaves | Statement: [Cephalotus, leafSpecialization, pitcher leaves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leafSpecialization Context triple: [Cephalotus, leafSpecialization, pitcher leaves]
-
A.
leafType
chosen
Indicates the specific kind or classification of leaf associated with an entity.
-
B.
branchSpecialization
Indicates that one branch or subdivision is specialized or focused in a particular area, function, or domain relative to others.
-
C.
laterSpecialization
Indicates that one entity becomes a more specialized or refined version of another entity at a later point in time.
-
D.
labelSpecialization
Indicates that one label is a more specific or specialized version of another label within a labeling or classification system.
-
E.
rangeSpecialization
Indicates that one entity is a more specific or constrained version of another entity within a defined range or scope.
- 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_69f76e24bbd0819096b837d35371639a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.