Triple
T27936331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valiant & Valiant |
E700621
|
entity |
| Predicate | officeFeature |
P127000
|
FINISHED |
| Object | desk and filing cabinets |
—
|
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: desk and filing cabinets | Statement: [Valiant & Valiant, officeFeature, desk and filing cabinets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeFeature Context triple: [Valiant & Valiant, officeFeature, desk and filing cabinets]
-
A.
officeIncludes
chosen
Indicates that an office contains, encompasses, or has within its scope a specified subordinate space, role, or resource.
-
B.
officeAction
Indicates an official act or decision taken by an office or authority in response to a matter, request, or proceeding.
-
C.
supportsOffice
Indicates that one entity provides assistance, resources, or endorsement to an office or officeholder in performing its functions or maintaining its operations.
-
D.
documentFeature
Indicates that a document possesses, exhibits, or is characterized by a particular feature or attribute.
-
E.
defaultOfficeSuite
Indicates that a particular office software suite is set as the primary or standard choice to be used by default.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: April 27, 2026, 7:13 p.m.