Triple
T32100015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porphyro |
E819819
|
entity |
| Predicate | visitManner |
P86122
|
FINISHED |
| Object | secretly |
—
|
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: secretly | Statement: [Porphyro, visitManner, secretly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitManner Context triple: [Porphyro, visitManner, secretly]
-
A.
hasManner
chosen
Indicates the way, style, or method in which an action is performed or a relation is carried out.
-
B.
visitorPractice
Indicates that a visitor engages in or performs a particular practice, activity, or routine.
-
C.
visitorIs
Indicates that one entity is acting in the role or capacity of a visitor with respect to another entity.
-
D.
visitorCustom
Indicates that one entity is a visitor in a customized or non-standard capacity to another entity, often with special conditions, attributes, or behaviors defined for that visit.
-
E.
visitorService
Indicates a relationship where a service is provided specifically for or to visitors, such as assistance, information, or support during their visit.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:26 a.m.