Triple
T3671483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AIP Conference Proceedings |
E77888
|
entity |
| Predicate | citationUse |
P40781
|
FINISHED |
| Object | citable record of conference research |
—
|
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: citable record of conference research | Statement: [AIP Conference Proceedings, citationUse, citable record of conference research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citationUse Context triple: [AIP Conference Proceedings, citationUse, citable record of conference research]
-
A.
citationBy
Indicates that one work is cited or referenced by another work.
-
B.
usesCitation
chosen
Indicates that one entity supports or references its content by citing another entity as a source.
-
C.
citation
Indicates that one entity references, quotes, or otherwise acknowledges another entity as a source of information or authority.
-
D.
citations
Indicates that one entity references another as a source of information, evidence, or authority, typically in a scholarly or informational context.
-
E.
citationNumber
Indicates the specific numeric identifier assigned to a citation within a document or reference list.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc42de1bc819090e19dd0805f13a1 |
completed | March 8, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69adb84a20288190a092e4a1b045fe3f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.