Triple
T5223986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GC |
E117938
|
entity |
| Predicate | usedInFormalContexts |
P62128
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [GC, usedInFormalContexts, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInFormalContexts Context triple: [GC, usedInFormalContexts, true]
-
A.
usedInFormalTitleOf
Indicates that something is employed as part of the official or formal title of an entity.
-
B.
usedInSpokenForm
Indicates that something (such as a word, name, or expression) is employed in spoken language or oral communication.
-
C.
usedInformallyAlongside
Indicates that something is employed in an informal, non-standard way together with or in addition to something else.
-
D.
formalizedUnder
Indicates that something has been officially established, defined, or codified within the framework, authority, or provisions of a particular formal system, agreement, or institution.
-
E.
formalTerminationContext
Indicates a context in which a relationship, agreement, or engagement is formally brought to an end through an official or structured process.
- F. None of above. chosen
Provenance (4 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7abd3ed48190bfd8d2f2ca399741 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd78a89b608190b259d3d8658f8f7c |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:48 p.m.