Triple
T18773054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Cavity |
E459062
|
entity |
| Predicate | isLargelyClearedBy |
P124235
|
FINISHED |
| Object | past supernova explosions |
—
|
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: past supernova explosions | Statement: [Local Cavity, isLargelyClearedBy, past supernova explosions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLargelyClearedBy Context triple: [Local Cavity, isLargelyClearedBy, past supernova explosions]
-
A.
clearancePeriod
Indicates the span of time during which a particular authorization, permission, or clearance remains valid or in effect.
-
B.
majorClearancesDate
Indicates the date on which major clearances, approvals, or permits associated with the subject were granted or completed.
-
C.
clearingSystem
Indicates that one entity functions as the financial clearing mechanism or infrastructure used to settle transactions for another entity.
-
D.
siteClearedBy
chosen
Indicates that a particular site has been cleared or prepared as a result of actions performed by a specified agent or entity.
-
E.
clearanceRequired
Indicates that a specific level of authorization or security clearance is needed before the related action can be performed or access can be granted.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e593378a4081909cc1b0856fce7d7d |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.