Triple
T37533985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eniwetok Atoll |
E933140
|
entity |
| Predicate | otherNotableTest |
P137654
|
FINISHED |
| Object | Greenhouse series |
—
|
NE NERFINISHED |
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: Greenhouse series | Statement: [Eniwetok Atoll, otherNotableTest, Greenhouse series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: otherNotableTest Context triple: [Eniwetok Atoll, otherNotableTest, Greenhouse series]
-
A.
notableTestDeveloped
Indicates that an entity is recognized for having created or developed a particular test or testing method.
-
B.
notableTestSeries
chosen
Indicates that a test series is recognized as particularly significant, memorable, or historically important in its context.
-
C.
notableDemo
Indicates that an entity is particularly well known or recognized for a specific demonstration, example, or showcase.
-
D.
notableSingle
Indicates that the subject is particularly recognized or distinguished for one specific, individual instance (such as a single work, event, or achievement).
-
E.
notableTarget
Indicates that the subject is particularly significant, prominent, or noteworthy with respect to the specified target.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.