Triple
T10320634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Physical Society academic journals |
E242126
|
entity |
| Predicate | haveEditorialBoard |
P1392
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [American Physical Society academic journals, haveEditorialBoard, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveEditorialBoard Context triple: [American Physical Society academic journals, haveEditorialBoard, true]
-
A.
hasEditorialBoard
chosen
Indicates that an entity (such as a publication or journal) is overseen or governed by a specific editorial board.
-
B.
hasEditorialMission
Indicates that an entity maintains or follows a defined editorial mission or guiding editorial policy.
-
C.
hasEditorialPage
Indicates that an entity (typically a publication) includes or is associated with an editorial page.
-
D.
hasManagingEditor
Indicates that one entity serves as the managing editor responsible for overseeing the editorial operations of another entity.
-
E.
hasEditorialFocus
Indicates that an entity (such as a publication or section) is primarily concerned with or oriented around a particular editorial topic, theme, or subject area.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:50 a.m.