Triple
T4339931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Declarations (law) |
E97553
|
entity |
| Predicate | oftenEmbodiedIn |
P4755
|
FINISHED |
| Object | resolutions |
—
|
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: resolutions | Statement: [Declarations (law), oftenEmbodiedIn, resolutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenEmbodiedIn Context triple: [Declarations (law), oftenEmbodiedIn, resolutions]
-
A.
embodiedBy
chosen
Indicates that an abstract concept, role, or function is physically or concretely realized in a specific entity.
-
B.
hasPartIn
Indicates that an entity participates in or plays a role within a larger event, process, or composite entity.
-
C.
containedWith
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
-
D.
usedInPartOf
Indicates that something is utilized or plays a functional role within a specific component or subpart of a larger whole.
-
E.
isSubstrateOf
Indicates that one entity serves as the material or reactant upon which another entity (typically an enzyme or process) acts in a chemical or biochemical reaction.
- 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_69b3454662a481908fbcd0bbfaa3a0a4 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3516f92588190bdf004d8020c1203 |
completed | March 12, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:14 p.m.