Triple
T16785027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quill |
E407948
|
entity |
| Predicate | hasBiologicalType |
P40326
|
FINISHED |
| Object | humanoid aliens |
—
|
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: humanoid aliens | Statement: [Quill, hasBiologicalType, humanoid aliens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBiologicalType Context triple: [Quill, hasBiologicalType, humanoid aliens]
-
A.
hasBiologicalComponents
Indicates that an entity is composed of, contains, or is associated with one or more biological parts or substances.
-
B.
hasBiologicalKingdom
Indicates that a biological organism is classified as belonging to a particular kingdom in the taxonomic hierarchy.
-
C.
biologicalCharacteristic
chosen
Indicates that one entity possesses or exhibits a particular biological trait, feature, or property in relation to another.
-
D.
biologicalOrigin
Indicates that one entity originates from, is derived from, or is produced by a biological source or organism in relation to another entity.
-
E.
biologicalRole
Indicates the functional role or purpose that one biological entity has in relation to another or within a biological process.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b21996cc81909deb88545af7079f |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.