Triple
T5150711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SI second |
E116185
|
entity |
| Predicate | isBaseOf |
P2421
|
FINISHED |
| Object | SI derived units involving time |
—
|
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: SI derived units involving time | Statement: [SI second, isBaseOf, SI derived units involving time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBaseOf Context triple: [SI second, isBaseOf, SI derived units involving time]
-
A.
isBaseFor
chosen
Indicates that one entity serves as the foundational support, starting point, or underlying basis upon which another entity is built, developed, or depends.
-
B.
isBasedOn
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
-
C.
isMajorBaseIn
Indicates that a location serves as a primary or central base of operations within a specified area or organization.
-
D.
isParentOf
Indicates that one entity is the biological or legal parent of another entity.
-
E.
hasSupportBaseIn
Indicates that one entity maintains an operational or organizational base of support located in another entity.
- 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_69bd445d94788190b72e2cc563120995 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b0fbb88190851e2d7ae1bdcc09 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.