Triple
T35860179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida |
E1036923
|
entity |
| Predicate | hasStateReptile |
P14012
|
FINISHED |
| Object | American alligator |
—
|
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: American alligator | Statement: [Florida, hasStateReptile, American alligator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStateReptile Context triple: [Florida, hasStateReptile, American alligator]
-
A.
stateReptile
chosen
Indicates that a particular reptile is officially designated as the state reptile of a given political region or jurisdiction.
-
B.
hasReptileSpecies
Indicates that one entity possesses, contains, or is associated with a reptile species as part of its characteristics or composition.
-
C.
hasOfficialStateAnimal
Indicates that a political entity has a formally designated animal recognized as its official state symbol.
-
D.
hasStateInsect
Indicates that a state has designated a particular insect as its official state insect.
-
E.
stateAmphibianOf
Indicates that a particular amphibian species is officially recognized as the state amphibian of a given political region or jurisdiction.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a001540d4f881908a4688881875e774 |
completed | May 10, 2026, 5:18 a.m. |
| PD | Predicate disambiguation | batch_6a0014a8cdd88190a67a90a2df2c5e18 |
completed | May 10, 2026, 5:16 a.m. |
Created at: May 3, 2026, 4:06 p.m.