Triple
T26765363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lambda baryon |
E674922
|
entity |
| Predicate | hasDiscoveryEra |
P61044
|
FINISHED |
| Object | 1940s |
—
|
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: 1940s | Statement: [Lambda baryon, hasDiscoveryEra, 1940s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiscoveryEra Context triple: [Lambda baryon, hasDiscoveryEra, 1940s]
-
A.
discoveryEra
chosen
Indicates the historical period or era during which the entity was discovered or first identified.
-
B.
livedInEra
Indicates that an entity existed or was active during a particular historical era or time period.
-
C.
hasPrimaryEra
Indicates that an entity is chiefly associated with or belongs to a particular historical or temporal era.
-
D.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
-
E.
hasEraInfluence
Indicates that one era or time period has a significant impact on shaping the characteristics, developments, or outcomes of another.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 27, 2026, 3:59 a.m.