Triple
T5051099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phobos |
E113785
|
entity |
| Predicate | hasLikelyComposition |
P51231
|
FINISHED |
| Object | carbonaceous material |
—
|
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: carbonaceous material | Statement: [Phobos, hasLikelyComposition, carbonaceous material]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLikelyComposition Context triple: [Phobos, hasLikelyComposition, carbonaceous material]
-
A.
likelyComposition
chosen
Indicates that one entity is probably a component or constituent part of another entity, though this compositional relationship is uncertain or inferred rather than definite.
-
B.
hasComb
Indicates that an entity possesses or is equipped with a comb.
-
C.
hasSurfaceComposition
Indicates that one entity has a surface made up of, or characterized by, the material or composition specified by another entity.
-
D.
hasCloudComposition
Indicates that an atmospheric body or region possesses a specific composition or makeup of clouds.
-
E.
possiblePlaceOfComposition
Indicates that a location is a plausible or hypothesized place where a work was composed.
- 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7426fc8081908a8227f73168c235 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.