Triple
T11974211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mathews balancing test |
E284996
|
entity |
| Predicate | thirdFactor |
P102587
|
FINISHED |
| Object | government’s interest |
—
|
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: government’s interest | Statement: [Mathews balancing test, thirdFactor, government’s interest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdFactor Context triple: [Mathews balancing test, thirdFactor, government’s interest]
-
A.
thirdWord
Indicates that one entity is the third word in sequence within another entity (such as a text or phrase).
-
B.
thirdSingle
Indicates that an entity is the third single (e.g., third single release) associated with another entity, typically in a sequence such as from an album or artist.
-
C.
thirdElement
Indicates that one entity is the third element in an ordered sequence or tuple associated with another entity.
-
D.
thirdTier
Indicates that an entity occupies a third level or rank within a hierarchical structure or classification.
-
E.
thirdCreatedBy
Indicates that the third item in a sequence or set was created by a specified agent or creator.
- F. None of above. chosen
Provenance (4 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9039107e48190ae4c4efd6257dd3c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:46 p.m.