Triple
T750320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Lovelock |
E15432
|
entity |
| Predicate | viewedEarthAs |
P18771
|
FINISHED |
| Object | self-regulating system |
—
|
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: self-regulating system | Statement: [James Lovelock, viewedEarthAs, self-regulating system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewedEarthAs Context triple: [James Lovelock, viewedEarthAs, self-regulating system]
-
A.
visibleFromSpace
Indicates that something can be seen or detected from outer space, typically by astronauts or satellites in orbit around a celestial body.
-
B.
visibleFromEarth
Indicates that the object can be observed from Earth, either with the naked eye or with appropriate instruments, under suitable viewing conditions.
-
C.
viewOnMoon
Indicates that an entity has a visual perspective or observable view from the surface or vicinity of the Moon.
-
D.
forEarthApprox
Indicates an approximate or estimated value or condition as it pertains to Earth or an Earth-related context.
-
E.
viewOnMilkyWay
Indicates a relationship where an entity has a visual perspective or observational view directed toward the Milky Way.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a6304e0c8190827fb57c5cac2da9 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a5004f708190a984ee221716e19c |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a58c0a84819094f07658dc651b36 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:37 p.m.