Triple
T29446886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IS curve |
E746876
|
entity |
| Predicate | describesEquilibriumIn |
P166294
|
FINISHED |
| Object | goods market |
—
|
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: goods market | Statement: [IS curve, describesEquilibriumIn, goods market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesEquilibriumIn Context triple: [IS curve, describesEquilibriumIn, goods market]
-
A.
equilibriumProperty
chosen
Indicates that a property or condition holds specifically when the system is in a state of equilibrium.
-
B.
equilibriumFigure
Indicates a stable configuration or shape in which all acting forces or influences on an object or system are balanced.
-
C.
equilibriumControlled
Indicates that one entity maintains or regulates the equilibrium state or balance condition of another entity or system.
-
D.
isEquilibriumReaction
Indicates that a chemical reaction can proceed in both forward and reverse directions and can reach a dynamic equilibrium between reactants and products.
-
E.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 28, 2026, 3:28 p.m.