Triple
T10162337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAR |
E233919
|
entity |
| Predicate | reportNumber |
P26175
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [TAR, reportNumber, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportNumber Context triple: [TAR, reportNumber, 3]
-
A.
reporterNumber
Indicates the identifier or count associated with the reporter involved in a given event or relationship.
-
B.
report
Indicates that one entity formally provides information or an account about another entity, event, or situation, typically for documentation, communication, or evaluation purposes.
-
C.
reportType
Indicates the specific category or kind of report associated with an entity or action.
-
D.
reportsWithin
Indicates that one entity submits or delivers a report to another entity within a specified time frame or boundary.
-
E.
refnum
chosen
Indicates that an entity is associated with a specific reference number used to identify or track it.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5b5194819095645e9174897b0f |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:09 p.m.