Triple
T19450451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asteroids |
E486600
|
entity |
| Predicate | livesSystem |
P98678
|
FINISHED |
| Object | limited number of ships |
—
|
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: limited number of ships | Statement: [Asteroids, livesSystem, limited number of ships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livesSystem Context triple: [Asteroids, livesSystem, limited number of ships]
-
A.
hasLivesSystem
chosen
Indicates that an entity exists or operates within, or is governed by, a particular system of living or life-related organization.
-
B.
livesAccordingTo
Indicates that an entity conducts its life or behavior in alignment with a specified principle, rule, belief system, or standard.
-
C.
givesLifeTo
Indicates a relationship where one entity causes, enables, or sustains the existence, vitality, or functioning of another.
-
D.
isLiving
Indicates that an entity is currently alive or possesses life.
-
E.
supportsLife
Indicates that one entity provides conditions or resources that allow another entity to live, grow, or remain biologically viable.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338db7c081908793f23592ebef6b |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.