Triple
T29446977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marshallian demand |
E746877
|
entity |
| Predicate | aggregatedTo |
P68691
|
FINISHED |
| Object | market demand function |
—
|
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: market demand function | Statement: [Marshallian demand, aggregatedTo, market demand function]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aggregatedTo Context triple: [Marshallian demand, aggregatedTo, market demand function]
-
A.
consolidatedBy
Indicates that one entity has been merged, unified, or combined into a more cohesive whole by another entity.
-
B.
consolidatedAs
Indicates that one entity has been combined, merged, or unified into another entity to form a single consolidated whole.
-
C.
aggregationProperty
chosen
Indicates that one entity serves as an aggregation or summary of values or instances associated with another entity.
-
D.
aggregateRate
Indicates a combined or overall rate derived from multiple individual rates or components.
-
E.
consolidatedUnder
Indicates that one entity has been merged into and is now formally part of another, typically larger or parent, entity.
- 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_69f66b21ea908190ae69b3f802fadab1 |
completed | May 2, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:28 p.m.