Triple
T20582721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open series |
E505699
|
entity |
| Predicate | hasFormalConcern |
P47677
|
FINISHED |
| Object | relationship between line and field |
—
|
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: relationship between line and field | Statement: [Open series, hasFormalConcern, relationship between line and field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormalConcern Context triple: [Open series, hasFormalConcern, relationship between line and field]
-
A.
formalConcern
chosen
Indicates that one entity has an official or formally recognized interest, responsibility, or involvement regarding another entity or matter.
-
B.
hasFormalConstraint
Indicates that an entity is governed or restricted by an explicitly defined formal rule, condition, or limitation.
-
C.
hasFormalStatus
Indicates that an entity possesses an officially recognized or legally defined status within a formal system or context.
-
D.
raisedConcernAbout
Indicates that one entity has expressed worry, doubt, or objection regarding another entity or issue.
-
E.
hasManagementConcern
Indicates that one entity has responsibility, authority, or involvement in overseeing, directing, or managing another entity or activity.
- 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_69e0b4b9669c8190b8e81fc72817d42c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a90f7e34819086b1745dcd53ba25 |
completed | April 20, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.