Triple
T1550449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Science and Engineering Indicators report |
E33076
|
entity |
| Predicate | hasDataSource |
P8776
|
FINISHED |
| Object | federal statistical agencies |
—
|
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: federal statistical agencies | Statement: [Science and Engineering Indicators report, hasDataSource, federal statistical agencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDataSource Context triple: [Science and Engineering Indicators report, hasDataSource, federal statistical agencies]
-
A.
hasDataFields
Indicates that an entity possesses or is associated with specific data fields or attributes.
-
B.
hasDatabase
Indicates that an entity possesses, uses, or is associated with a specific database.
-
C.
hasLongTermDatasetSince
Indicates that an entity has maintained or used a particular dataset continuously starting from a specified point in time.
-
D.
hasColumns
Indicates that one entity possesses or is characterized by a set of columns associated with it.
-
E.
hasConnection
chosen
Indicates that there exists a link, association, or relationship between two entities.
- 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_69a885ee6db8819099502bc5ce8af881 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa574094048190a2d7fc3ac904d51e |
completed | March 6, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69a907b426dc8190975c024a50955368 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.