Triple
T7357923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pierre the Pelican |
E169671
|
entity |
| Predicate | speciesRepresentation |
P39361
|
FINISHED |
| Object | pelican |
—
|
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: pelican | Statement: [Pierre the Pelican, speciesRepresentation, pelican]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speciesRepresentation Context triple: [Pierre the Pelican, speciesRepresentation, pelican]
-
A.
speciesStructure
Indicates the structural or organizational characteristics that define how a species is composed or arranged.
-
B.
speciesNumber
Indicates the numerical identifier or count associated with a particular species in a given context.
-
C.
componentRepresents
chosen
Indicates that one component stands in for, symbolizes, or models another entity or concept within a system or context.
-
D.
regionRepresentation
Indicates that one entity serves as a representation, model, or depiction of a specific geographic or spatial region associated with another entity.
-
E.
populationRole
Indicates the role or function that an entity has within a population or demographic context.
- 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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26d6d6081909c7272a9ccae0d97 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f02d36108190bcb34a95e6a30bd7 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:06 p.m.