Triple
T28547363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hirundoidea |
E722479
|
entity |
| Predicate | typicalTailForm |
P12789
|
FINISHED |
| Object | often forked tail |
—
|
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: often forked tail | Statement: [Hirundoidea, typicalTailForm, often forked tail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTailForm Context triple: [Hirundoidea, typicalTailForm, often forked tail]
-
A.
hasTailShape
Indicates that an entity possesses a tail with a specific shape or form.
-
B.
tailCharacteristic
Indicates that an entity possesses a particular property, feature, or quality specifically related to its tail.
-
C.
typicalForm
chosen
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
typicalConclusion
Indicates that one entity is the usual or expected outcome, result, or ending that follows from another entity or situation.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a00b8e0a5508190abc5c1e492bed12e |
completed | May 10, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_6a00b8327d048190850af317f60f0f8b |
completed | May 10, 2026, 4:54 p.m. |
Created at: April 28, 2026, 3:40 a.m.