Triple
T9294168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S/1501 |
E223597
|
entity |
| Predicate | associatedResolutionNumber |
P86565
|
FINISHED |
| Object | 82 |
—
|
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: 82 | Statement: [S/1501, associatedResolutionNumber, 82]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedResolutionNumber Context triple: [S/1501, associatedResolutionNumber, 82]
-
A.
involvedResolution
Indicates that an entity participated in or contributed to the process of resolving a particular issue, conflict, or problem.
-
B.
issueNumber
chosen
Indicates the specific numeric identifier assigned to distinguish one issue from others within a series or collection.
-
C.
resolutionLeadsTo
Indicates that achieving a particular resolution or decision directly brings about or causes a subsequent outcome or state.
-
D.
resolvedIn
Indicates that an issue, conflict, or process is brought to a conclusion or solution within a specified context, medium, or timeframe.
-
E.
reinforcedByResolution
Indicates that something is strengthened, supported, or made more effective as a result of a specific resolution or formal decision.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd089a2ed0819086b2e4219ff2453e |
completed | April 1, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.