Triple
T8247746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arch Wiki |
E192888
|
entity |
| Predicate | notablePage |
P28873
|
FINISHED |
| Object | Beginners' guide |
—
|
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: Beginners' guide | Statement: [Arch Wiki, notablePage, Beginners' guide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePage Context triple: [Arch Wiki, notablePage, Beginners' guide]
-
A.
notableArticle
chosen
Indicates that there exists an article or written work that is especially significant, prominent, or noteworthy in relation to the subject.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
D.
notableSection
Indicates that a particular part or segment of something is especially important, prominent, or worthy of attention within the whole.
-
E.
notableMagazine
Indicates that a person or entity is notably associated with a particular magazine, such as by being featured in, writing for, or significantly contributing to 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7875318c819095f971ba513c54fd |
completed | March 31, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.