Triple
T24822335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | maxwell |
E621093
|
entity |
| Predicate | belongsToUnitFamily |
P4276
|
FINISHED |
| Object | electromagnetic CGS units |
—
|
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: electromagnetic CGS units | Statement: [maxwell, belongsToUnitFamily, electromagnetic CGS units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToUnitFamily Context triple: [maxwell, belongsToUnitFamily, electromagnetic CGS units]
-
A.
belongsToFamily
chosen
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
B.
belongsToPackageFamily
Indicates that one item is a member of, or associated with, a specific package family.
-
C.
belongsToFlagFamily
Indicates that one flag is a member of, or classified under, a particular flag family or group.
-
D.
belongsToDynamicalFamily
Indicates that one entity is a member of, or classified within, a specific dynamical family defined by shared motion or evolution characteristics.
-
E.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 5:04 a.m.