Triple
T123770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLOSS debate |
E2501
|
entity |
| Predicate | involvesConcept |
P531
|
FINISHED |
| Object | single large reserve |
—
|
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: single large reserve | Statement: [SLOSS debate, involvesConcept, single large reserve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesConcept Context triple: [SLOSS debate, involvesConcept, single large reserve]
-
A.
hasConcept
chosen
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
B.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
C.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
D.
challengedConcept
Indicates that one entity has questioned, disputed, or called into doubt the validity, accuracy, or applicability of a particular concept.
-
E.
demonstratedConcept
Indicates that an entity has shown, illustrated, or made evident a particular concept through example, explanation, or action.
- 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_69a251b54ea88190b18281669f59b4c0 |
completed | Feb. 28, 2026, 2:23 a.m. |
| NER | Named-entity recognition | batch_69a2573ce0ac8190b49fb31d3d475bf9 |
completed | Feb. 28, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69a2564928208190966a619680a0d6e2 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:27 a.m.