Triple
T15305759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symbolic Lodge |
E365892
|
entity |
| Predicate | keepsRecord |
P72845
|
FINISHED |
| Object | minutes of meetings |
—
|
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: minutes of meetings | Statement: [Symbolic Lodge, keepsRecord, minutes of meetings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keepsRecord Context triple: [Symbolic Lodge, keepsRecord, minutes of meetings]
-
A.
recordKeeper
chosen
Indicates a relationship where one entity is responsible for maintaining, managing, or preserving official records or documented information about another entity or activity.
-
B.
recordKeepingSystem
Indicates a relationship where an entity functions as or is associated with a system used to store, manage, and maintain records or information.
-
C.
recordHeld
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
-
D.
statusRecordedBy
Indicates that the status of an entity was documented or captured by a specific agent or system.
-
E.
poweredRecord
Indicates that one entity functions as a powered or electrified version of another entity, typically enabling enhanced or active operation.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ccef14c819099c5ebe962e7f867 |
completed | April 16, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.