Triple
T125675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lawyers’ Edition |
E2544
|
entity |
| Predicate | isUnofficialReporter |
P4154
|
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: [Lawyers’ Edition, isUnofficialReporter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUnofficialReporter Context triple: [Lawyers’ Edition, isUnofficialReporter, true]
-
A.
officiallyReports
Indicates that one entity formally provides information, updates, or accountability to another entity within an official or authorized reporting structure.
-
B.
reporter
Indicates that an entity acts in the role of a reporter, typically gathering, writing, or presenting information or news about another entity or event.
-
C.
hasInformalStatus
chosen
Indicates that an entity holds a non-official, casual, or unofficial standing or role in relation to another entity.
-
D.
isOfficialPortalFor
Indicates that one entity serves as the recognized, authoritative portal or entry point for accessing information or services related to another entity.
-
E.
canReport
Indicates that one entity has the ability or permission to report on, or submit a report about, another entity or situation.
- 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_69a251b54ea88190b18281669f59b4c0 |
completed | Feb. 28, 2026, 2:23 a.m. |
| NER | Named-entity recognition | batch_69a2573e4e6481908252dfef2e34f46e |
completed | Feb. 28, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69a2564a54948190ba30bee858173b27 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:27 a.m.