Triple
T9625740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erathem |
E232458
|
entity |
| Predicate | formalStatus |
P18869
|
FINISHED |
| Object | formal unit |
—
|
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: formal unit | Statement: [Erathem, formalStatus, formal unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalStatus Context triple: [Erathem, formalStatus, formal unit]
-
A.
hasFormalStatus
chosen
Indicates that an entity possesses an officially recognized or legally defined status within a formal system or context.
-
B.
statusFormula
Indicates a formal expression or rule that defines or evaluates the current status or condition of something.
-
C.
hasInformalStatus
Indicates that an entity holds a non-official, casual, or unofficial standing or role in relation to another entity.
-
D.
nominalStatus
Indicates that an entity holds a particular title, label, or status in name or designation, without necessarily implying associated functions or actions.
-
E.
isFormalizedBy
Indicates that something is given a defined, structured, or official form through a specific method, process, or representation.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9afb67c88190aa170716f0033752 |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.