Triple
T37353827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croc Files |
E927397
|
entity |
| Predicate | featuresPresenterRole |
P205850
|
FINISHED |
| Object | wildlife expert |
—
|
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: wildlife expert | Statement: [Croc Files, featuresPresenterRole, wildlife expert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPresenterRole Context triple: [Croc Files, featuresPresenterRole, wildlife expert]
-
A.
featuresPublisher
Indicates that one entity highlights, showcases, or gives prominent placement to a publisher.
-
B.
displayRole
Indicates the role or position an entity holds in the context of how it is presented or shown in a display.
-
C.
featuresHero
Indicates that something (such as a work, product, or story) prominently includes or centers around a particular hero as a main character or focus.
-
D.
featuresEarlyProminentRoleFor
Indicates that something includes another entity in an early and prominently visible or important role.
-
E.
featuresOnScreenPerformer
Indicates that something (such as a work or production) includes a particular performer visibly appearing on screen.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:16 p.m.