Triple
T2173737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARPES |
E48479
|
entity |
| Predicate | dataRepresentedAs |
P21655
|
FINISHED |
| Object | intensity maps in energy-momentum space |
—
|
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: intensity maps in energy-momentum space | Statement: [ARPES, dataRepresentedAs, intensity maps in energy-momentum space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataRepresentedAs Context triple: [ARPES, dataRepresentedAs, intensity maps in energy-momentum space]
-
A.
representationType
chosen
Indicates the specific form or mode in which something is represented or expressed (e.g., as a symbol, image, model, or description).
-
B.
dataTypes
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
-
C.
dataModel
Indicates a relationship where an entity defines, uses, or is structured according to a specific data model or schema.
-
D.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
E.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
- 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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc1559ff481908efe3f214b2570dc |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbd9efc1c81909a65044a1ffc9038 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.