Triple
T4585068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hemichordata |
E101947
|
entity |
| Predicate | resemblesInFeature |
P35666
|
FINISHED |
| Object | Chordata in having pharyngeal slits |
—
|
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: Chordata in having pharyngeal slits | Statement: [Hemichordata, resemblesInFeature, Chordata in having pharyngeal slits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resemblesInFeature Context triple: [Hemichordata, resemblesInFeature, Chordata in having pharyngeal slits]
-
A.
resembles
chosen
Indicates that one entity is similar in appearance, form, or characteristics to another.
-
B.
isFeatureOf
Indicates that something functions as a characteristic, attribute, or component belonging to or describing another entity.
-
C.
featureParityWith
Indicates that two entities offer the same or equivalent set of features or capabilities.
-
D.
materiallySimilarTo
Indicates that two entities share substantially the same physical or material characteristics, composition, or properties, though they may not be exactly identical.
-
E.
isFeatureBased
Indicates that one entity is derived from, determined by, or constructed using the characteristics or attributes of another entity.
- 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59056bb48190ba1e0b5beda9bdc4 |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.