Triple
T21763323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max-E3-LIN-2 |
E537215
|
entity |
| Predicate | baselineRandomAssignmentSatisfaction |
P83418
|
FINISHED |
| Object | 1/2 |
—
|
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: 1/2 | Statement: [Max-E3-LIN-2, baselineRandomAssignmentSatisfaction, 1/2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baselineRandomAssignmentSatisfaction Context triple: [Max-E3-LIN-2, baselineRandomAssignmentSatisfaction, 1/2]
-
A.
isRandomized
chosen
Indicates that the selection, ordering, or assignment associated with something is determined by a random process rather than a fixed or predetermined rule.
-
B.
surveyEnd
Indicates that a survey has been completed or has reached its designated end point.
-
C.
approvalRate
Indicates the proportion or percentage of subjects that express approval or a positive evaluation toward a given entity or action.
-
D.
usesSurveyOf
Indicates that one entity bases its work, analysis, or decision on data or findings obtained from a particular survey conducted by another entity.
-
E.
politicalExperiment
Indicates an action or process in which political ideas, systems, or policies are tried out or tested to observe their effects or viability.
- 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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031a711dc8190a786c9849dc344e8 |
completed | April 28, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:51 p.m.