Triple
T20392751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andorians |
E498122
|
entity |
| Predicate | antennaeSensitivity |
P139964
|
FINISHED |
| Object | highly sensitive to damage |
—
|
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: highly sensitive to damage | Statement: [Andorians, antennaeSensitivity, highly sensitive to damage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antennaeSensitivity Context triple: [Andorians, antennaeSensitivity, highly sensitive to damage]
-
A.
antennaType
Indicates the specific kind or category of antenna associated with an entity or connection.
-
B.
numberOfAntennas
Indicates the quantity of antennas that an entity possesses or is associated with.
-
C.
hasExternalAntenna
Indicates that an entity is equipped with or connected to an antenna located outside its main body or enclosure.
-
D.
numberOfAntennasInitial
Indicates the initial count of antennas associated with an entity before any changes or updates occur.
-
E.
notableAntenna
Indicates that an entity possesses an antenna that is particularly significant, prominent, or noteworthy in some relevant context.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6791144788190a0ab42cf0141b6a3 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:28 a.m.