Triple
T4535512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosgrave |
E107398
|
entity |
| Predicate | fieldAssociated |
P2830
|
FINISHED |
| Object | politics |
—
|
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: politics | Statement: [Cosgrave, fieldAssociated, politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldAssociated Context triple: [Cosgrave, fieldAssociated, politics]
-
A.
relatedField
Indicates that one field, topic, or area of study is connected or relevant to another in subject matter or application.
-
B.
fieldRepresents
Indicates that one field or attribute stands for, encodes, or symbolizes another concept, value, or entity.
-
C.
fieldAdvanced
Indicates that a particular field or attribute has progressed beyond a basic or standard level, reflecting a more complex, specialized, or developed state.
-
D.
isAssociatedWith
chosen
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
E.
leaderAssociatedWith
Indicates a relationship where a leader is connected or affiliated with a particular entity, such as an organization, group, or cause.
- 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_69bd43f922788190b7edfa294e39b178 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57b634b08190845d04213cf8d5b9 |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521edd00819099dfccaa65dddd61 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:04 p.m.