Triple
T30617077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aspidella |
E779341
|
entity |
| Predicate | functionalInterpretation |
P175687
|
FINISHED |
| Object | holdfast structure |
—
|
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: holdfast structure | Statement: [Aspidella, functionalInterpretation, holdfast structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionalInterpretation Context triple: [Aspidella, functionalInterpretation, holdfast structure]
-
A.
featuresInterpretationsOf
Indicates that one entity presents or includes interpretive representations, analyses, or renditions of another entity.
-
B.
intendedInterpretation
Indicates that one entity is meant to be understood or interpreted in a particular way, sense, or meaning relative to another.
-
C.
interpretationFacility
Indicates that an entity serves as a facility or venue where interpretation (such as language or translation services) is provided or supported.
-
D.
eraInterpreted
Indicates that one entity has been interpreted, understood, or given meaning by another entity.
-
E.
frequentlyInterpretedBy
Indicates that an entity is often or regularly interpreted, explained, or given meaning by a particular agent or group.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: April 29, 2026, 8:26 p.m.