Triple
T30959108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truffula seed |
E788758
|
entity |
| Predicate | potentialToBecome |
P58576
|
FINISHED |
| Object | Truffula tree |
—
|
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: Truffula tree | Statement: [Truffula seed, potentialToBecome, Truffula tree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: potentialToBecome Context triple: [Truffula seed, potentialToBecome, Truffula tree]
-
A.
willBecome
Indicates that one entity is expected or destined to change state or identity into another entity in the future.
-
B.
hasPotential
chosen
Indicates that an entity possesses the capacity or possibility to develop, achieve, or exhibit a particular state, quality, or outcome in the future.
-
C.
exportPotential
Indicates the extent to which something is suitable or likely to be successfully exported to other markets or locations.
-
D.
agingPotential
Indicates the capacity or suitability of something to improve, develop, or remain effective over time as it ages.
-
E.
couldBePromotedTo
Indicates a potential or eligibility for one entity to be advanced or elevated to a higher role, status, or position relative to another.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:54 p.m.